Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e146753cfd8f3d44f812ac77a0bb1fdc2b058ed5021113d31c7163884092a0ee

Tx prefix hash: e026cd8cd40e8067d8f6b9d6c3645402d6d018bccc6652e1220963aa73b4f9c2
Tx public key: 47fceea851551456919a5d84835519c517f4dfaca17036237a70ce985ef51e4a
Timestamp: 1630779487 Timestamp [UCT]: 2021-09-04 18:18:07 Age [y:d:h:m:s]: 03:184:01:45:21
Block: 327449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 906155 RingCT/type: yes/0
Extra: 0147fceea851551456919a5d84835519c517f4dfaca17036237a70ce985ef51e4a02110000003151fa4013000000000000000000

1 output(s) for total of 50.470029106000 dcy

stealth address amount amount idx
00: f1f1707a8f4d9d47e0ac8b750904b29d77ba1b6398b2838060cc766d3e81f1bc 50.470029106000 678134 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": 327459, "vin": [ { "gen": { "height": 327449 } } ], "vout": [ { "amount": 50470029106, "target": { "key": "f1f1707a8f4d9d47e0ac8b750904b29d77ba1b6398b2838060cc766d3e81f1bc" } } ], "extra": [ 1, 71, 252, 238, 168, 81, 85, 20, 86, 145, 154, 93, 132, 131, 85, 25, 197, 23, 244, 223, 172, 161, 112, 54, 35, 122, 112, 206, 152, 94, 245, 30, 74, 2, 17, 0, 0, 0, 49, 81, 250, 64, 19, 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