Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47821a8fedc78262633afd716f1c7c5092afb19fb36dfa141a4136fa9d1d780b

Tx prefix hash: 745ac496e6be60849f7d13bfda4f82b21e532fe81abee88fe49e1b3a5483a58c
Tx public key: 5cc45fa751a03114a3a949313cd6c6459b80a6f03127ea8badd21d9699d7e2f3
Timestamp: 1747229815 Timestamp [UCT]: 2025-05-14 13:36:55 Age [y:d:h:m:s]: 00:146:20:01:27
Block: 1282782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102572 RingCT/type: yes/0
Extra: 015cc45fa751a03114a3a949313cd6c6459b80a6f03127ea8badd21d9699d7e2f302110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35e90a64d66bd7fa0a04fda0e3b4ec7b7577f554e4f452ca8e2868a1f4219c74 0.600000000000 1770193 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": 1282792, "vin": [ { "gen": { "height": 1282782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35e90a64d66bd7fa0a04fda0e3b4ec7b7577f554e4f452ca8e2868a1f4219c74" } } ], "extra": [ 1, 92, 196, 95, 167, 81, 160, 49, 20, 163, 169, 73, 49, 60, 214, 198, 69, 155, 128, 166, 240, 49, 39, 234, 139, 173, 210, 29, 150, 153, 215, 226, 243, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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