Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7c1f3da2e05b7b70312896209d1cf8270b94af20503ed8b70d995423dba5b30

Tx prefix hash: 5e993d1a6c46de57a3f39e3279d270a47928443d033ed8075ef6dc906637b6f6
Tx public key: c67074d2111db48f11b445beac52a0b3e742698453b0f8a26cac8679574681dc
Timestamp: 1648491395 Timestamp [UCT]: 2022-03-28 18:16:35 Age [y:d:h:m:s]: 02:232:08:45:24
Block: 468376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 685574 RingCT/type: yes/0
Extra: 01c67074d2111db48f11b445beac52a0b3e742698453b0f8a26cac8679574681dc021100000003cb8520c2000000000000000000

1 output(s) for total of 17.221704446000 dcy

stealth address amount amount idx
00: 0c491c6681962b9736768b242f0e123b2933a44bd36dffcb05ed2b80a5a3f8fb 17.221704446000 887082 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": 468386, "vin": [ { "gen": { "height": 468376 } } ], "vout": [ { "amount": 17221704446, "target": { "key": "0c491c6681962b9736768b242f0e123b2933a44bd36dffcb05ed2b80a5a3f8fb" } } ], "extra": [ 1, 198, 112, 116, 210, 17, 29, 180, 143, 17, 180, 69, 190, 172, 82, 160, 179, 231, 66, 105, 132, 83, 176, 248, 162, 108, 172, 134, 121, 87, 70, 129, 220, 2, 17, 0, 0, 0, 3, 203, 133, 32, 194, 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