Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9d13c32a6abac81691456c2fe0b041f5795f6d76d94e21a4fffdd0bee9d3d24

Tx prefix hash: 40eb056346d7083dbd462ddc0a77c9d4722db13cd2bbe975570ce9d7b2161f3c
Tx public key: d3552bd05925f8406eb7ded2fd4764a248d34a9112672f277b991f8d4030e6bf
Timestamp: 1673246085 Timestamp [UCT]: 2023-01-09 06:34:45 Age [y:d:h:m:s]: 02:048:16:52:28
Block: 670795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556466 RingCT/type: yes/0
Extra: 01d3552bd05925f8406eb7ded2fd4764a248d34a9112672f277b991f8d4030e6bf0211000000018b7b6602000000000000000000

1 output(s) for total of 3.676018267000 dcy

stealth address amount amount idx
00: 3ae721019dd9a2734abc449146d57ace58df2a8c5f660842d0716b7b65532e99 3.676018267000 1112216 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": 670805, "vin": [ { "gen": { "height": 670795 } } ], "vout": [ { "amount": 3676018267, "target": { "key": "3ae721019dd9a2734abc449146d57ace58df2a8c5f660842d0716b7b65532e99" } } ], "extra": [ 1, 211, 85, 43, 208, 89, 37, 248, 64, 110, 183, 222, 210, 253, 71, 100, 162, 72, 211, 74, 145, 18, 103, 47, 39, 123, 153, 31, 141, 64, 48, 230, 191, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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