Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84eca0fdad79eff357dbfaae86660094d65a130872638448b2574a6837d375cd

Tx prefix hash: 305f5f04a1f7598bd61c192473ac913465115d14f24be94d367b90941b97f18d
Tx public key: be25ede52dcb5d36c5604d60d1942f1d24e90d49f22d8c3c53dfd4868f4eac81
Timestamp: 1581946888 Timestamp [UCT]: 2020-02-17 13:41:28 Age [y:d:h:m:s]: 04:358:04:38:27
Block: 66698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148267 RingCT/type: yes/0
Extra: 01be25ede52dcb5d36c5604d60d1942f1d24e90d49f22d8c3c53dfd4868f4eac8102110000000156c366d3000000000000000000

1 output(s) for total of 368.979847356000 dcy

stealth address amount amount idx
00: 47c19d0c09a910d86e2616f97d6d013e36f1a8b3f3acabcf3f069c7ff7347f49 368.979847356000 122863 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": 66708, "vin": [ { "gen": { "height": 66698 } } ], "vout": [ { "amount": 368979847356, "target": { "key": "47c19d0c09a910d86e2616f97d6d013e36f1a8b3f3acabcf3f069c7ff7347f49" } } ], "extra": [ 1, 190, 37, 237, 229, 45, 203, 93, 54, 197, 96, 77, 96, 209, 148, 47, 29, 36, 233, 13, 73, 242, 45, 140, 60, 83, 223, 212, 134, 143, 78, 172, 129, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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