Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30c13cac24223a72818def1924a1dc3a1b1989fb8a75fb4d30cd68e6f2a24e0a

Tx prefix hash: fc74c213cc7324ad564f1397e0a8d3f1f7130ebbdbcba133625237ba90bb483c
Tx public key: 6bf6f896b787c1203e37deec99ecb00b9d88e9aa3b81181e21b645d1dac8c60e
Timestamp: 1757198812 Timestamp [UTC]: 2025-09-06 22:46:52 Age [y:d:h:m:s]: 01:074:11:12:30
Block: 1362937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319667 RingCT/type: yes/0
Extra: 016bf6f896b787c1203e37deec99ecb00b9d88e9aa3b81181e21b645d1dac8c60e021100000008b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a41c86e965832c705b702fbfddc52cb7874bb8a5734023a4079626f726552ca2 0.000600000000 1850976 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": 1362947, "vin": [ { "gen": { "height": 1362937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a41c86e965832c705b702fbfddc52cb7874bb8a5734023a4079626f726552ca2" } } ], "extra": [ 1, 107, 246, 248, 150, 183, 135, 193, 32, 62, 55, 222, 236, 153, 236, 176, 11, 157, 136, 233, 170, 59, 129, 24, 30, 33, 182, 69, 209, 218, 200, 198, 14, 2, 17, 0, 0, 0, 8, 178, 247, 132, 196, 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: