Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 313b54bcef747cabd68302dc79d2d632687b4b1401e65161bf20edc99fc78382

Tx prefix hash: 1db9995f98fe10a2684f3306e8406d8f913c16b9661d9b8af3ffe9783e293cf8
Tx public key: 54f8bf4e9147956996d3ae7c71b409a299d5acd7dc282106c4ec44bc9f611445
Timestamp: 1760705850 Timestamp [UTC]: 2025-10-17 12:57:30 Age [y:d:h:m:s]: 01:029:03:10:52
Block: 1391917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287092 RingCT/type: yes/0
Extra: 0154f8bf4e9147956996d3ae7c71b409a299d5acd7dc282106c4ec44bc9f6114450211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fbc801ef59e01f2a1fa0efae2566398eecc98524399b1302faf3603efe14cedb 0.000600000000 1880166 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": 1391927, "vin": [ { "gen": { "height": 1391917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbc801ef59e01f2a1fa0efae2566398eecc98524399b1302faf3603efe14cedb" } } ], "extra": [ 1, 84, 248, 191, 78, 145, 71, 149, 105, 150, 211, 174, 124, 113, 180, 9, 162, 153, 213, 172, 215, 220, 40, 33, 6, 196, 236, 68, 188, 159, 97, 20, 69, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: