Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07048a525fe4311c505e2216036e03ce0f80ea260c7c589ab1f9b903d9f1407c

Tx prefix hash: 4c939e033389910c39dde4519b3afd5a5c876d0b341e710d7714be3cc308e2f8
Tx public key: 0da4a03ec3d0fa1b49fe8adf4194d0751b85736875e5f6af0e71119dd604b99e
Timestamp: 1644454938 Timestamp [UCT]: 2022-02-10 01:02:18 Age [y:d:h:m:s]: 03:033:14:51:14
Block: 435350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 803879 RingCT/type: yes/0
Extra: 010da4a03ec3d0fa1b49fe8adf4194d0751b85736875e5f6af0e71119dd604b99e021100000003a272b9cb000000000000000000

1 output(s) for total of 22.156697471000 dcy

stealth address amount amount idx
00: 4c43ea41bd7ad64b4f56e8e6d5b1e402c8d85d072c2a5c1f23cebcd4001ff225 22.156697471000 846509 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": 435360, "vin": [ { "gen": { "height": 435350 } } ], "vout": [ { "amount": 22156697471, "target": { "key": "4c43ea41bd7ad64b4f56e8e6d5b1e402c8d85d072c2a5c1f23cebcd4001ff225" } } ], "extra": [ 1, 13, 164, 160, 62, 195, 208, 250, 27, 73, 254, 138, 223, 65, 148, 208, 117, 27, 133, 115, 104, 117, 229, 246, 175, 14, 113, 17, 157, 214, 4, 185, 158, 2, 17, 0, 0, 0, 3, 162, 114, 185, 203, 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