Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46b565c1370f44d79e6b20593af00fb6cf68f3a277bef5f3fbac9de33cff49fb

Tx prefix hash: 22a02cef6f470474b356590d8dc1204469efd848328ba8eb5c043d50a826a3a2
Tx public key: f9297b91071e8efa41a55d870e0f956935d48732498fac9f42647d565d945fad
Timestamp: 1714454242 Timestamp [UCT]: 2024-04-30 05:17:22 Age [y:d:h:m:s]: 00:332:04:05:30
Block: 1011578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237445 RingCT/type: yes/0
Extra: 01f9297b91071e8efa41a55d870e0f956935d48732498fac9f42647d565d945fad02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fde4de9d0e07ebb0c846d8a0ead71412acdee96b4c770dd6aa262a5e1ad6496 0.600000000000 1473844 of 15

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": 1011588, "vin": [ { "gen": { "height": 1011578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fde4de9d0e07ebb0c846d8a0ead71412acdee96b4c770dd6aa262a5e1ad6496" } } ], "extra": [ 1, 249, 41, 123, 145, 7, 30, 142, 250, 65, 165, 93, 135, 14, 15, 149, 105, 53, 212, 135, 50, 73, 143, 172, 159, 66, 100, 125, 86, 93, 148, 95, 173, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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