Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ad863d131a873eeb71b3d49952958d26e5a6b8f10c8d583ee9576a83cf06fd9

Tx prefix hash: 7a5154ac4b2d55f8f56145a44e7e77a64391331fed412ad7509bad435cef547a
Tx public key: 112046186057bfeeecf27f7361f64f3e4f98277e4310a97937e29f115aebe442
Timestamp: 1685477162 Timestamp [UTC]: 2023-05-30 20:06:02 Age [y:d:h:m:s]: 03:173:23:17:20
Block: 771597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 910505 RingCT/type: yes/0
Extra: 01112046186057bfeeecf27f7361f64f3e4f98277e4310a97937e29f115aebe442021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.001703644617 xmr

stealth address amount amount idx tag
00: 6acf64c4280e0dc85f14428d5fb7164589c1cd7db1182274385371781239b125 0.001703644617 1220970 of 0 -

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": 771607, "vin": [ { "gen": { "height": 771597 } } ], "vout": [ { "amount": 1703644617, "target": { "key": "6acf64c4280e0dc85f14428d5fb7164589c1cd7db1182274385371781239b125" } } ], "extra": [ 1, 17, 32, 70, 24, 96, 87, 191, 238, 236, 242, 127, 115, 97, 246, 79, 62, 79, 152, 39, 126, 67, 16, 169, 121, 55, 226, 159, 17, 90, 235, 228, 66, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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: