Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f55d72eae2296e3b765f7078fb3d05464c9c4c71bf0b7d967fef462994e43d8

Tx prefix hash: dc798e0e0434e47974540d1b4dc307dde76d450922fdcc0a4a096159d3ff342e
Tx public key: 22a0976454724d41ab0f53b83c3344f41bb85820ab2b192d6ffaf51289dcd0e8
Timestamp: 1715636005 Timestamp [UCT]: 2024-05-13 21:33:25 Age [y:d:h:m:s]: 00:178:07:03:40
Block: 1021365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127640 RingCT/type: yes/0
Extra: 0122a0976454724d41ab0f53b83c3344f41bb85820ab2b192d6ffaf51289dcd0e80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a51fbad3a4d3538ab7b5c0d06533a4075b39b54f1f4a2c5337ada1bc2342b0b0 0.600000000000 1485666 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": 1021375, "vin": [ { "gen": { "height": 1021365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a51fbad3a4d3538ab7b5c0d06533a4075b39b54f1f4a2c5337ada1bc2342b0b0" } } ], "extra": [ 1, 34, 160, 151, 100, 84, 114, 77, 65, 171, 15, 83, 184, 60, 51, 68, 244, 27, 184, 88, 32, 171, 43, 25, 45, 111, 250, 245, 18, 137, 220, 208, 232, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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