Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fac753178c3da66507c540ea6c340af45eb4f6a8bc27083bc6488245a3e46e51

Tx prefix hash: 341ffb98e3dfc49251c5de667636adc762882d4d252f1552fa0739b761df9b73
Tx public key: 318a4e4e60bd8ac02a7ec7ced532f5eced890ffcf7b945cc59e4a8c6b9df001c
Timestamp: 1722565423 Timestamp [UCT]: 2024-08-02 02:23:43 Age [y:d:h:m:s]: 00:294:21:08:21
Block: 1078821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210691 RingCT/type: yes/0
Extra: 01318a4e4e60bd8ac02a7ec7ced532f5eced890ffcf7b945cc59e4a8c6b9df001c02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42f8d3491f920c68dd908a52c90468ca53586900667904d4a66e94fda41a334d 0.600000000000 1551516 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": 1078831, "vin": [ { "gen": { "height": 1078821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42f8d3491f920c68dd908a52c90468ca53586900667904d4a66e94fda41a334d" } } ], "extra": [ 1, 49, 138, 78, 78, 96, 189, 138, 192, 42, 126, 199, 206, 213, 50, 245, 236, 237, 137, 15, 252, 247, 185, 69, 204, 89, 228, 168, 198, 185, 223, 0, 28, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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