Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f588512be6f6402245aa17c96bad88f32346eb87d6aded7e63381cb021eea7b3

Tx prefix hash: 7a9b0a97aae069de4243cf11bf26ceb92284d3816701dc511d3b79eb6923ce77
Tx public key: 6611cd85fcba775a54baebd47a9adb9fa414236b193d0246b9109e8d1fa43cb2
Timestamp: 1728361184 Timestamp [UCT]: 2024-10-08 04:19:44 Age [y:d:h:m:s]: 00:257:20:59:47
Block: 1126874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183936 RingCT/type: yes/0
Extra: 016611cd85fcba775a54baebd47a9adb9fa414236b193d0246b9109e8d1fa43cb2021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4dfdc74dbd24cb3b3fa8bcabfd5f777d96e12305af70758e0c5dbf1e74bdeb1 0.600000000000 1609671 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": 1126884, "vin": [ { "gen": { "height": 1126874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4dfdc74dbd24cb3b3fa8bcabfd5f777d96e12305af70758e0c5dbf1e74bdeb1" } } ], "extra": [ 1, 102, 17, 205, 133, 252, 186, 119, 90, 84, 186, 235, 212, 122, 154, 219, 159, 164, 20, 35, 107, 25, 61, 2, 70, 185, 16, 158, 141, 31, 164, 60, 178, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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