Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19295536ef81ca9fc0054e27dae142cfcda9c54a62cfafb6eaa4bafd44f68ba5

Tx prefix hash: 87421f6b6e96b6067367d18aa76def2afae6b2d501d87653a62d6708c92c4b7f
Tx public key: 32531c7ae2ede80771bc6d20143526ac53badce021e5e3354921da7f113f513d
Timestamp: 1770922665 Timestamp [UTC]: 2026-02-12 18:57:45 Age [y:d:h:m:s]: 00:279:17:38:26
Block: 1476403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205481 RingCT/type: yes/0
Extra: 0132531c7ae2ede80771bc6d20143526ac53badce021e5e3354921da7f113f513d021100000038e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1c89ccfd4ccf8dbb02d6189ee959868a49d1f4fa9cffb6c250c123ccc36d9824 0.000600000000 1965709 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": 1476413, "vin": [ { "gen": { "height": 1476403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c89ccfd4ccf8dbb02d6189ee959868a49d1f4fa9cffb6c250c123ccc36d9824" } } ], "extra": [ 1, 50, 83, 28, 122, 226, 237, 232, 7, 113, 188, 109, 32, 20, 53, 38, 172, 83, 186, 220, 224, 33, 229, 227, 53, 73, 33, 218, 127, 17, 63, 81, 61, 2, 17, 0, 0, 0, 56, 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: