Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35277d6f3e8c953d69ecfe47ee17b3306aa6ddf3de7084de671768997cedfaee

Tx prefix hash: 95e3e7a6dd85bf30534877cf68d0a860a03dbef48ae3844264f17f21a6ad2ee8
Tx public key: d1734045a6418f8acff829dc91c20297502d3f4936c34e366e025f5f61e08877
Timestamp: 1703360446 Timestamp [UTC]: 2023-12-23 19:40:46 Age [y:d:h:m:s]: 02:331:01:42:48
Block: 919600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 761794 RingCT/type: yes/0
Extra: 01d1734045a6418f8acff829dc91c20297502d3f4936c34e366e025f5f61e088770211000000010011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5f1f970ca5ef7f90f5bb60d7f09af1afdf9e6f1a9d52b997e363da89778784fb 0.000600000000 1377276 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": 919610, "vin": [ { "gen": { "height": 919600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f1f970ca5ef7f90f5bb60d7f09af1afdf9e6f1a9d52b997e363da89778784fb" } } ], "extra": [ 1, 209, 115, 64, 69, 166, 65, 143, 138, 207, 248, 41, 220, 145, 194, 2, 151, 80, 45, 63, 73, 54, 195, 78, 54, 110, 2, 95, 95, 97, 224, 136, 119, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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: