Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71ffb18f2a36a34ab921e85be1a47235e446e61c79aa2c22064d0a2e0069f0a0

Tx prefix hash: 8b79f61aef7a9a4678cf762b3500237440bda1c0bd414682e3494b31bb74f793
Tx public key: dac74c43ff6eb6f361ebf1bffc3a3dd2e955e94dfc1739fe7638ef4b1f830404
Timestamp: 1715274301 Timestamp [UTC]: 2024-05-09 17:05:01 Age [y:d:h:m:s]: 02:001:07:48:36
Block: 1018382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513147 RingCT/type: yes/0
Extra: 01dac74c43ff6eb6f361ebf1bffc3a3dd2e955e94dfc1739fe7638ef4b1f8304040211000000030011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5c1f96556a93fd2f0e750ef4669e0e0c0a5dc4d9d55fc48a430858fef1edbf3b 0.000600000000 1482171 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 dinastycoin-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": 1018392, "vin": [ { "gen": { "height": 1018382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c1f96556a93fd2f0e750ef4669e0e0c0a5dc4d9d55fc48a430858fef1edbf3b" } } ], "extra": [ 1, 218, 199, 76, 67, 255, 110, 182, 243, 97, 235, 241, 191, 252, 58, 61, 210, 233, 85, 233, 77, 252, 23, 57, 254, 118, 56, 239, 75, 31, 131, 4, 4, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: