Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e84ac0b6a3ab830dde2b3f23afc3d306a32bf8b5eafbbbfacbff4e00c364a1c

Tx prefix hash: b338b469f3931a65864cc48482745d44ad808010dbbc61d83af2df7cd1d6f1ed
Tx public key: 1fd7065b50adc927a30102a1ab57ab62b8489e04a9190047bb056041fe0efe07
Timestamp: 1755639067 Timestamp [UTC]: 2025-08-19 21:31:07 Age [y:d:h:m:s]: 01:091:10:11:05
Block: 1350125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331605 RingCT/type: yes/0
Extra: 011fd7065b50adc927a30102a1ab57ab62b8489e04a9190047bb056041fe0efe0702110000000be4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2cbd47c8f286f833a2fcd0fc31df44e38c67ff0e0487092349408437e627158e 0.000600000000 1838066 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": 1350135, "vin": [ { "gen": { "height": 1350125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cbd47c8f286f833a2fcd0fc31df44e38c67ff0e0487092349408437e627158e" } } ], "extra": [ 1, 31, 215, 6, 91, 80, 173, 201, 39, 163, 1, 2, 161, 171, 87, 171, 98, 184, 72, 158, 4, 169, 25, 0, 71, 187, 5, 96, 65, 254, 14, 254, 7, 2, 17, 0, 0, 0, 11, 228, 220, 144, 9, 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: