Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 356628c84d5808a0f49ed9a2dcdc524660a733729d41ccc3bbf4dbad40396948

Tx prefix hash: 379ce4a7aca87f3cc3181f250cbadc854bc0a832ba5f51cd10a9cba3a40419fd
Tx public key: 6acaae3dfb8b2172d9aa354a5c03c080fb962b76207cc867d524d22fe8746929
Timestamp: 1772282809 Timestamp [UTC]: 2026-02-28 12:46:49 Age [y:d:h:m:s]: 00:072:21:34:13
Block: 1487637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44403 RingCT/type: yes/0
Extra: 016acaae3dfb8b2172d9aa354a5c03c080fb962b76207cc867d524d22fe8746929021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3b566c9c37ecb4b1910f59c72f0cdc66792f3f8bee9801630b0b68443ab8ee1d 0.000600000000 1977107 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": 1487647, "vin": [ { "gen": { "height": 1487637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b566c9c37ecb4b1910f59c72f0cdc66792f3f8bee9801630b0b68443ab8ee1d" } } ], "extra": [ 1, 106, 202, 174, 61, 251, 139, 33, 114, 217, 170, 53, 74, 92, 3, 192, 128, 251, 150, 43, 118, 32, 124, 200, 103, 213, 36, 210, 47, 232, 116, 105, 41, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: