Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a8b491d5e17bf32e31d8e804f3c6630cbe3465276fc5989558cd2fde616646f

Tx prefix hash: fb60863317f24d254b7672e363a256b51cf4054c98190c248754e5f0a5417f14
Tx public key: 7c1a31ba83c0a0e2a3deea10d7b9f8a0dbdc9ae4fd2b3c4ed790ade5b37b9070
Timestamp: 1742062795 Timestamp [UCT]: 2025-03-15 18:19:55 Age [y:d:h:m:s]: 00:282:18:30:02
Block: 1240018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199849 RingCT/type: yes/0
Extra: 017c1a31ba83c0a0e2a3deea10d7b9f8a0dbdc9ae4fd2b3c4ed790ade5b37b907002110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 434629c4f7bb0ce70301021922bde6d021709d44fccc1fc40cbe4c661c25b1f5 0.600000000000 1726983 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 dinasty-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": 1240028, "vin": [ { "gen": { "height": 1240018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "434629c4f7bb0ce70301021922bde6d021709d44fccc1fc40cbe4c661c25b1f5" } } ], "extra": [ 1, 124, 26, 49, 186, 131, 192, 160, 226, 163, 222, 234, 16, 215, 185, 248, 160, 219, 220, 154, 228, 253, 43, 60, 78, 215, 144, 173, 229, 179, 123, 144, 112, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8