Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e77b4cef5d45fa78d02625bb3d53a4e7ed8c36932fdc83f4fbc3777e633edc5

Tx prefix hash: e2851038b07dbe10d902ac5049b1c9d109de6c40649a3ed521d81f51af8e5520
Tx public key: 189a2d96fb78a20013b2c359190dd4fcd03706f65b1c801bc3362e15f609d078
Timestamp: 1733323661 Timestamp [UCT]: 2024-12-04 14:47:41 Age [y:d:h:m:s]: 00:195:06:56:49
Block: 1167910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139299 RingCT/type: yes/0
Extra: 01189a2d96fb78a20013b2c359190dd4fcd03706f65b1c801bc3362e15f609d0780211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 237dde1a6376939c84f17bc40bc7744e84e04af76a9c0e4039da6421802cb9e9 0.600000000000 1653615 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": 1167920, "vin": [ { "gen": { "height": 1167910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "237dde1a6376939c84f17bc40bc7744e84e04af76a9c0e4039da6421802cb9e9" } } ], "extra": [ 1, 24, 154, 45, 150, 251, 120, 162, 0, 19, 178, 195, 89, 25, 13, 212, 252, 208, 55, 6, 246, 91, 28, 128, 27, 195, 54, 46, 21, 246, 9, 208, 120, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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