Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72d4a0071a0ed82ff4e361ab687ce685e60eeef8991aec6051ec46056e1d0536

Tx prefix hash: 7761c68f7c50bf1aaaba94a84ed40979c4d3a33f2ed45dbaf8de8bf0b029cde3
Tx public key: 37746e622d9f8ada7dbe96d460bc8c594d8b89e7609126c2c8210f375d111a0a
Timestamp: 1737378841 Timestamp [UTC]: 2025-01-20 13:14:01 Age [y:d:h:m:s]: 01:299:09:42:34
Block: 1201435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477784 RingCT/type: yes/0
Extra: 0137746e622d9f8ada7dbe96d460bc8c594d8b89e7609126c2c8210f375d111a0a021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fac923b5c156316710a0adfe61f25a7af97253adc5c7b476d4d7716226a6379e 0.000600000000 1688088 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": 1201445, "vin": [ { "gen": { "height": 1201435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fac923b5c156316710a0adfe61f25a7af97253adc5c7b476d4d7716226a6379e" } } ], "extra": [ 1, 55, 116, 110, 98, 45, 159, 138, 218, 125, 190, 150, 212, 96, 188, 140, 89, 77, 139, 137, 231, 96, 145, 38, 194, 200, 33, 15, 55, 93, 17, 26, 10, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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: