Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a082d2db13a0f372cf674630d44a61542e37d23c3856ef876d551d3ee9012cf4

Tx prefix hash: 31b87c0b252296e73cdb64299d830202a7e591611b977aacde0d6ad0d79d3fd7
Tx public key: 990deb1f35ff0ed7e9dc56007a5441150fbc66e332f1133f5a2f4005166e4db8
Timestamp: 1702316149 Timestamp [UCT]: 2023-12-11 17:35:49 Age [y:d:h:m:s]: 01:133:15:49:30
Block: 910949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356667 RingCT/type: yes/0
Extra: 01990deb1f35ff0ed7e9dc56007a5441150fbc66e332f1133f5a2f4005166e4db802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10639c831b2bb78900e1d3df45be9f088a6495152cc6b2023bcfd965e41188a3 0.600000000000 1368124 of 15

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": 910959, "vin": [ { "gen": { "height": 910949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10639c831b2bb78900e1d3df45be9f088a6495152cc6b2023bcfd965e41188a3" } } ], "extra": [ 1, 153, 13, 235, 31, 53, 255, 14, 215, 233, 220, 86, 0, 122, 84, 65, 21, 15, 188, 102, 227, 50, 241, 19, 63, 90, 47, 64, 5, 22, 110, 77, 184, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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