Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f803d88db73e805f8c4dbf2189b41a743c5e96929f36735c40f64abd0216dc

Tx prefix hash: 5c84fe5f3570f9015028f5451a50c67e34cf273facbb7da56392c95693663853
Tx public key: 502f6fdc489be0302adb332f017590d7afc37d500ddde50b1f21e134de72c48e
Timestamp: 1578072349 Timestamp [UCT]: 2020-01-03 17:25:49 Age [y:d:h:m:s]: 05:030:18:25:01
Block: 37861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171897 RingCT/type: yes/0
Extra: 01502f6fdc489be0302adb332f017590d7afc37d500ddde50b1f21e134de72c48e021100000008d81c26c0000000000000000000

1 output(s) for total of 459.781656818000 dcy

stealth address amount amount idx
00: 8c3a6c30216891540c3bf8f0b524a169a0d1dc75189cf92f08fd2688fc47c17c 459.781656818000 64390 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": 37871, "vin": [ { "gen": { "height": 37861 } } ], "vout": [ { "amount": 459781656818, "target": { "key": "8c3a6c30216891540c3bf8f0b524a169a0d1dc75189cf92f08fd2688fc47c17c" } } ], "extra": [ 1, 80, 47, 111, 220, 72, 155, 224, 48, 42, 219, 51, 47, 1, 117, 144, 215, 175, 195, 125, 80, 13, 221, 229, 11, 31, 33, 225, 52, 222, 114, 196, 142, 2, 17, 0, 0, 0, 8, 216, 28, 38, 192, 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