Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa302cfd2bf393cc871dc36d86aef6460649c8b4882575995c2461c304ca93c1

Tx prefix hash: 3bd486e586c8242861b537f89d455d7140e54e5c79de359172f7f9eaf7d5e9f3
Tx public key: 7bb297c8a689408005c8273b10873d125e37b347a20b02f7f0c082dc85cfa0be
Timestamp: 1742227522 Timestamp [UTC]: 2025-03-17 16:05:22 Age [y:d:h:m:s]: 01:071:20:44:25
Block: 1241374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303983 RingCT/type: yes/0
Extra: 017bb297c8a689408005c8273b10873d125e37b347a20b02f7f0c082dc85cfa0be021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3fdb5bb51ffff9267ebb4aa05708ee8a63b9f89de4b84ae8d3a3ef906313e341 0.000600000000 1728347 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": 1241384, "vin": [ { "gen": { "height": 1241374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fdb5bb51ffff9267ebb4aa05708ee8a63b9f89de4b84ae8d3a3ef906313e341" } } ], "extra": [ 1, 123, 178, 151, 200, 166, 137, 64, 128, 5, 200, 39, 59, 16, 135, 61, 18, 94, 55, 179, 71, 162, 11, 2, 247, 240, 192, 130, 220, 133, 207, 160, 190, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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: