Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b749b426bf2f3dbf0d89f73e4dc40f9b611d0a176e6e1ec68ae55c27c49b6011

Tx prefix hash: 8a0cda0a50e695261904065b8a69abe301538d6a74dc53a82b2317bbe6c52ecd
Tx public key: defba4526715f9974281300cc71ddfb6344e6e819acb78c32dddf18f48a70e65
Timestamp: 1745484623 Timestamp [UTC]: 2025-04-24 08:50:23 Age [y:d:h:m:s]: 01:211:23:24:00
Block: 1268326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415168 RingCT/type: yes/0
Extra: 01defba4526715f9974281300cc71ddfb6344e6e819acb78c32dddf18f48a70e650211000000086c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 65fe7e6c75f95c304ac9ddd09b2eaa3a282f9492b3d360dadc9587984b3bd458 0.000600000000 1755555 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": 1268336, "vin": [ { "gen": { "height": 1268326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65fe7e6c75f95c304ac9ddd09b2eaa3a282f9492b3d360dadc9587984b3bd458" } } ], "extra": [ 1, 222, 251, 164, 82, 103, 21, 249, 151, 66, 129, 48, 12, 199, 29, 223, 182, 52, 78, 110, 129, 154, 203, 120, 195, 45, 221, 241, 143, 72, 167, 14, 101, 2, 17, 0, 0, 0, 8, 108, 152, 170, 61, 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: