Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 025c88769c2508266f7d2d957f54e20229b17d31b32b491b349928c83bdec479

Tx prefix hash: 02eecfba6ae19244a65faf81a5ecb0f873de2ca67e82fc61a3c5cab9b058d42b
Tx public key: 14ed49e6008e1e1c8872114832692be36aa8486ca703835548ce8e99660fb2bc
Timestamp: 1589362109 Timestamp [UCT]: 2020-05-13 09:28:29 Age [y:d:h:m:s]: 05:172:12:15:22
Block: 100355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1301847 RingCT/type: yes/0
Extra: 0114ed49e6008e1e1c8872114832692be36aa8486ca703835548ce8e99660fb2bc0211000003c845705818000000000000000000

1 output(s) for total of 285.455640216000 dcy

stealth address amount amount idx
00: 3fc2c51661f560d34391a977cafd84f421fc2d1cbffd6ec3991b2517f1e067a0 285.455640216000 176855 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": 100365, "vin": [ { "gen": { "height": 100355 } } ], "vout": [ { "amount": 285455640216, "target": { "key": "3fc2c51661f560d34391a977cafd84f421fc2d1cbffd6ec3991b2517f1e067a0" } } ], "extra": [ 1, 20, 237, 73, 230, 0, 142, 30, 28, 136, 114, 17, 72, 50, 105, 43, 227, 106, 168, 72, 108, 167, 3, 131, 85, 72, 206, 142, 153, 102, 15, 178, 188, 2, 17, 0, 0, 3, 200, 69, 112, 88, 24, 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