Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 985856031be4ce0eb44e122eb555c951470e9dffe9db1a703e4eb9aac07a42e8

Tx prefix hash: 13ad26526ec9929ce6f90178e86f25c95113665ce231bd1be1d4c6f4fcbe1246
Tx public key: 7363347b4ff26a03883c361fd197583db8d65b0bdf24aeb5c4ae917bbe0a0f1d
Timestamp: 1699832291 Timestamp [UCT]: 2023-11-12 23:38:11 Age [y:d:h:m:s]: 01:065:12:21:40
Block: 890367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308216 RingCT/type: yes/0
Extra: 017363347b4ff26a03883c361fd197583db8d65b0bdf24aeb5c4ae917bbe0a0f1d0211000000082f2199b8000000000000000000

1 output(s) for total of 0.688405795000 dcy

stealth address amount amount idx
00: 1e64e09cd19071e36a56d2eb94bd88fd0fd01f67374329f4b564387097cd8e30 0.688405795000 1346390 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": 890377, "vin": [ { "gen": { "height": 890367 } } ], "vout": [ { "amount": 688405795, "target": { "key": "1e64e09cd19071e36a56d2eb94bd88fd0fd01f67374329f4b564387097cd8e30" } } ], "extra": [ 1, 115, 99, 52, 123, 79, 242, 106, 3, 136, 60, 54, 31, 209, 151, 88, 61, 184, 214, 91, 11, 223, 36, 174, 181, 196, 174, 145, 123, 190, 10, 15, 29, 2, 17, 0, 0, 0, 8, 47, 33, 153, 184, 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