Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2318f711509d104feb698dd52dc4bbb026b715a2d220bdde28123b9a0551ec11

Tx prefix hash: 261cecb1cc3ab8305cea1aea936ea0d1be7e51225be7bf6c436c7f7ae6a3fe45
Tx public key: e465202fc4d0540a676e44510002978ddb39dd9dc9ce87014c3397fc75f233a8
Timestamp: 1700071979 Timestamp [UTC]: 2023-11-15 18:12:59 Age [y:d:h:m:s]: 03:005:12:41:14
Block: 892347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 790139 RingCT/type: yes/0
Extra: 01e465202fc4d0540a676e44510002978ddb39dd9dc9ce87014c3397fc75f233a8021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.000678084712 xmr

stealth address amount amount idx tag
00: 60c7381bf0a4adc71bec44e94351ba35aea77bf929eeb9988c033035afaa0c0d 0.000678084712 1348466 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 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": 892357, "vin": [ { "gen": { "height": 892347 } } ], "vout": [ { "amount": 678084712, "target": { "key": "60c7381bf0a4adc71bec44e94351ba35aea77bf929eeb9988c033035afaa0c0d" } } ], "extra": [ 1, 228, 101, 32, 47, 196, 208, 84, 10, 103, 110, 68, 81, 0, 2, 151, 141, 219, 57, 221, 157, 201, 206, 135, 1, 76, 51, 151, 252, 117, 242, 51, 168, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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: