Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dda3fe89db288f21c3eb28f20b02b5911ae123a9479c03e063ebaa581c4b1784

Tx prefix hash: 7b23d87ef0327639577bcc59bfb948446e0fa6bc54e4afa84d44674d3de798a1
Tx public key: 5530b0c006c45ae71701fd2fd6c1aefb2aa728b938ae31e79b381ceba1a6fadf
Timestamp: 1700428659 Timestamp [UCT]: 2023-11-19 21:17:39 Age [y:d:h:m:s]: 01:101:01:36:35
Block: 895297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333377 RingCT/type: yes/0
Extra: 015530b0c006c45ae71701fd2fd6c1aefb2aa728b938ae31e79b381ceba1a6fadf0211000000024b8f5122000000000000000000

1 output(s) for total of 0.662993658000 dcy

stealth address amount amount idx
00: 0fd847866dc837d441bde3b1ecf585e0f0b323fd3627b1a261ed070c4b0188d6 0.662993658000 1351526 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 895307, "vin": [ { "gen": { "height": 895297 } } ], "vout": [ { "amount": 662993658, "target": { "key": "0fd847866dc837d441bde3b1ecf585e0f0b323fd3627b1a261ed070c4b0188d6" } } ], "extra": [ 1, 85, 48, 176, 192, 6, 196, 90, 231, 23, 1, 253, 47, 214, 193, 174, 251, 42, 167, 40, 185, 56, 174, 49, 231, 155, 56, 28, 235, 161, 166, 250, 223, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8