Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85f831ab1f236501a1ca6203caeb157351d6892c929d09b860f73a42961b52b8

Tx prefix hash: 21a730b58e05cb83b8539bdd28099fa466ea6a23bf809a928006fc12e3137797
Tx public key: 22c9044b743ed2dd8c8cbf5a1c229f55453e473e4d0d7499c92deb7bc0909646
Timestamp: 1677678331 Timestamp [UCT]: 2023-03-01 13:45:31 Age [y:d:h:m:s]: 02:042:18:23:18
Block: 707566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552152 RingCT/type: yes/0
Extra: 0122c9044b743ed2dd8c8cbf5a1c229f55453e473e4d0d7499c92deb7bc09096460211000000055029cbac000000000000000000

1 output(s) for total of 2.776770710000 dcy

stealth address amount amount idx
00: 50984ee8414e0f3f8781ad74334cb5e630e6b8e70e6c030014685d002a54d4e9 2.776770710000 1151381 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": 707576, "vin": [ { "gen": { "height": 707566 } } ], "vout": [ { "amount": 2776770710, "target": { "key": "50984ee8414e0f3f8781ad74334cb5e630e6b8e70e6c030014685d002a54d4e9" } } ], "extra": [ 1, 34, 201, 4, 75, 116, 62, 210, 221, 140, 140, 191, 90, 28, 34, 159, 85, 69, 62, 71, 62, 77, 13, 116, 153, 201, 45, 235, 123, 192, 144, 150, 70, 2, 17, 0, 0, 0, 5, 80, 41, 203, 172, 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