Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b4d1e11876109e72d1c2f6b7a1ba91446aae1f2ce6fceec459fb994c8378781

Tx prefix hash: 96f9047c2ae2552f46fa24033664bedcb84553be6b9da66b6b8fb34136ce828f
Tx public key: 0ee59476a00a3ff3539d46626aa287f738963ce1cc0fd4d3b0ccf78ce84e053a
Timestamp: 1702017172 Timestamp [UCT]: 2023-12-08 06:32:52 Age [y:d:h:m:s]: 01:101:02:25:38
Block: 908471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333399 RingCT/type: yes/0
Extra: 010ee59476a00a3ff3539d46626aa287f738963ce1cc0fd4d3b0ccf78ce84e053a02110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deb8605f57de78bde99f9e45abdd4a14e5ee7fa00e7cbe1cfdf5cb5d6017ca86 0.600000000000 1365504 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": 908481, "vin": [ { "gen": { "height": 908471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deb8605f57de78bde99f9e45abdd4a14e5ee7fa00e7cbe1cfdf5cb5d6017ca86" } } ], "extra": [ 1, 14, 229, 148, 118, 160, 10, 63, 243, 83, 157, 70, 98, 106, 162, 135, 247, 56, 150, 60, 225, 204, 15, 212, 211, 176, 204, 247, 140, 232, 78, 5, 58, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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