Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d6ca47ec227f4643cfa7489f10054c6dd8522d91a34b3afedaf070625083b98

Tx prefix hash: 038bb20bc2a756a6b92b2c6c63e9d380a7388ca45312f6b1a6bbdea9b83fb528
Tx public key: f4151f4fe31dcac8db3548d09ebbf6af7c68a701f5a7891730e9ac4f4a251f18
Timestamp: 1743164574 Timestamp [UTC]: 2025-03-28 12:22:54 Age [y:d:h:m:s]: 01:042:08:32:56
Block: 1249117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281497 RingCT/type: yes/0
Extra: 01f4151f4fe31dcac8db3548d09ebbf6af7c68a701f5a7891730e9ac4f4a251f180211000000019ba629df000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7f017b233faeb5e67be5c4125a47069fcb8e4c7a05d1517459d0333042235a7a 0.000600000000 1736152 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": 1249127, "vin": [ { "gen": { "height": 1249117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f017b233faeb5e67be5c4125a47069fcb8e4c7a05d1517459d0333042235a7a" } } ], "extra": [ 1, 244, 21, 31, 79, 227, 29, 202, 200, 219, 53, 72, 208, 158, 187, 246, 175, 124, 104, 167, 1, 245, 167, 137, 23, 48, 233, 172, 79, 74, 37, 31, 24, 2, 17, 0, 0, 0, 1, 155, 166, 41, 223, 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: