Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e40b66906c3cca7a59fc0d7c015de5016b60bd1560ae03c1742686bb524c9833

Tx prefix hash: c0ebe8b96f163c3016693cc5ee036b9d9de95e5d94ab38da202d6369f8af9ea4
Tx public key: 69f72711f8cd5abcb29f346c079530c93aa771f347556fc36e8e537f6009f750
Timestamp: 1687214987 Timestamp [UCT]: 2023-06-19 22:49:47 Age [y:d:h:m:s]: 01:249:13:37:50
Block: 786004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439494 RingCT/type: yes/0
Extra: 0169f72711f8cd5abcb29f346c079530c93aa771f347556fc36e8e537f6009f750021100000001faf35c9c000000000000000000

1 output(s) for total of 1.526309518000 dcy

stealth address amount amount idx
00: e25b123f59184620d65402950600f8d4f910a48a74b45a0fd00728d8bee89f2c 1.526309518000 1235981 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": 786014, "vin": [ { "gen": { "height": 786004 } } ], "vout": [ { "amount": 1526309518, "target": { "key": "e25b123f59184620d65402950600f8d4f910a48a74b45a0fd00728d8bee89f2c" } } ], "extra": [ 1, 105, 247, 39, 17, 248, 205, 90, 188, 178, 159, 52, 108, 7, 149, 48, 201, 58, 167, 113, 243, 71, 85, 111, 195, 110, 142, 83, 127, 96, 9, 247, 80, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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