Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c950c5770855e955aba5298ed010cd5261728f5eef4ce76fb663a1b02d67e2b

Tx prefix hash: b485a73a618d1c4bfbe8cf3c91be8e0faf60b5e3cb3385422d07f4d2bb768bb4
Tx public key: 653661f2b74422c0b15c6d7e5afd7477803daca2471f212d277cb90dfcafa659
Timestamp: 1748581425 Timestamp [UTC]: 2025-05-30 05:03:45 Age [y:d:h:m:s]: 01:175:13:02:34
Block: 1293971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389523 RingCT/type: yes/0
Extra: 01653661f2b74422c0b15c6d7e5afd7477803daca2471f212d277cb90dfcafa65902110000000843846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 385f2bb957c40d4830f107e1c8ebb65e18aa280104997d156695acb8cf1f1679 0.000600000000 1781466 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": 1293981, "vin": [ { "gen": { "height": 1293971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "385f2bb957c40d4830f107e1c8ebb65e18aa280104997d156695acb8cf1f1679" } } ], "extra": [ 1, 101, 54, 97, 242, 183, 68, 34, 192, 177, 92, 109, 126, 90, 253, 116, 119, 128, 61, 172, 162, 71, 31, 33, 45, 39, 124, 185, 13, 252, 175, 166, 89, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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: