Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fecab8ca5ff860acfa1134181bc81bc20337eea15996edc47bd82fcf5e35a6b

Tx prefix hash: 7ae725032a56313e5d0abb9ad2353aa188f8aab7b73ccfdcdd7a71bdd03a1f66
Tx public key: 3c834fa9f6245995f75938432a94ffa16fdc0c606a70e8ee3bbb2587e4a36295
Timestamp: 1719445480 Timestamp [UCT]: 2024-06-26 23:44:40 Age [y:d:h:m:s]: 00:355:16:48:14
Block: 1052948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254118 RingCT/type: yes/0
Extra: 013c834fa9f6245995f75938432a94ffa16fdc0c606a70e8ee3bbb2587e4a3629502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a85c47c0518b45f00a687592943a2e08d7fd68a3c867699e5d596639c0e8c85 0.600000000000 1523293 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": 1052958, "vin": [ { "gen": { "height": 1052948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a85c47c0518b45f00a687592943a2e08d7fd68a3c867699e5d596639c0e8c85" } } ], "extra": [ 1, 60, 131, 79, 169, 246, 36, 89, 149, 247, 89, 56, 67, 42, 148, 255, 161, 111, 220, 12, 96, 106, 112, 232, 238, 59, 187, 37, 135, 228, 163, 98, 149, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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