Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c62c08a8de268a5315b1745dd4c166b54978b9979c69110efdae2d01b950284

Tx prefix hash: c92f796925bcfc04f7c988cdd516d66de6215fb0b81c5fefe5cf7f86d2c8e49f
Tx public key: 1d2e563a62664f6836945c133c64ea01af431b09dd7a464fe2eb66a626fa627f
Timestamp: 1574723405 Timestamp [UCT]: 2019-11-25 23:10:05 Age [y:d:h:m:s]: 05:181:17:55:54
Block: 17498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1272539 RingCT/type: yes/0
Extra: 011d2e563a62664f6836945c133c64ea01af431b09dd7a464fe2eb66a626fa627f02110000001321bf71c4000000000000000000

1 output(s) for total of 537.170569889000 dcy

stealth address amount amount idx
00: 452487469ce2270a1d8f00cd0c34d6e88a69c68ef2ef76b13ee6cfce30fd9774 537.170569889000 25498 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": 17508, "vin": [ { "gen": { "height": 17498 } } ], "vout": [ { "amount": 537170569889, "target": { "key": "452487469ce2270a1d8f00cd0c34d6e88a69c68ef2ef76b13ee6cfce30fd9774" } } ], "extra": [ 1, 29, 46, 86, 58, 98, 102, 79, 104, 54, 148, 92, 19, 60, 100, 234, 1, 175, 67, 27, 9, 221, 122, 70, 79, 226, 235, 102, 166, 38, 250, 98, 127, 2, 17, 0, 0, 0, 19, 33, 191, 113, 196, 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