Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b716144bdd874a4e8e4aab5ca41e18631fdb3f505657f3e2e74192d6c19fece1

Tx prefix hash: 0f41f935146706a7f1425ffdfd5b370822d280f68c6c5b71a81264c65de5d41a
Tx public key: dfa76247292c5d5aee3878e1d8e08a0c8fb1ef588499a5ce630617b1caef29a5
Timestamp: 1699240373 Timestamp [UCT]: 2023-11-06 03:12:53 Age [y:d:h:m:s]: 00:320:12:24:24
Block: 885444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229593 RingCT/type: yes/0
Extra: 01dfa76247292c5d5aee3878e1d8e08a0c8fb1ef588499a5ce630617b1caef29a5021100000007faf35c9c000000000000000000

1 output(s) for total of 0.714753791000 dcy

stealth address amount amount idx
00: ec2d544b420e14f099d04bb473ea1e6bfb795dc53d5133013350d88a96a7673b 0.714753791000 1341213 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": 885454, "vin": [ { "gen": { "height": 885444 } } ], "vout": [ { "amount": 714753791, "target": { "key": "ec2d544b420e14f099d04bb473ea1e6bfb795dc53d5133013350d88a96a7673b" } } ], "extra": [ 1, 223, 167, 98, 71, 41, 44, 93, 90, 238, 56, 120, 225, 216, 224, 138, 12, 143, 177, 239, 88, 132, 153, 165, 206, 99, 6, 23, 177, 202, 239, 41, 165, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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