Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25a48feef656413c713e01a6a3478cd63ace8753ceada67ecea5e59a8bd468fd

Tx prefix hash: a44fa5ee0dbbce0ea81fbe9b2c0c70c89c19986e74a7a084a5460b1055bbb1a8
Tx public key: df66a4403cb55132248362804325d5227a5c0262a99bc2e9abcad930312f3e56
Timestamp: 1636692051 Timestamp [UCT]: 2021-11-12 04:40:51 Age [y:d:h:m:s]: 03:087:17:51:20
Block: 372571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 841092 RingCT/type: yes/0
Extra: 01df66a4403cb55132248362804325d5227a5c0262a99bc2e9abcad930312f3e56021100000064f56b629f000000000000000000

1 output(s) for total of 35.772513056000 dcy

stealth address amount amount idx
00: b69e754f28c6eeba1ad52d6b87174879e99b6a0d8fd22334e6a1c814d8662886 35.772513056000 754689 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": 372581, "vin": [ { "gen": { "height": 372571 } } ], "vout": [ { "amount": 35772513056, "target": { "key": "b69e754f28c6eeba1ad52d6b87174879e99b6a0d8fd22334e6a1c814d8662886" } } ], "extra": [ 1, 223, 102, 164, 64, 60, 181, 81, 50, 36, 131, 98, 128, 67, 37, 213, 34, 122, 92, 2, 98, 169, 155, 194, 233, 171, 202, 217, 48, 49, 47, 62, 86, 2, 17, 0, 0, 0, 100, 245, 107, 98, 159, 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