Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 177bbcc34bd7f41a10c4c996b611bdf127a5def250b4139644756b1c69c8f684

Tx prefix hash: 25d37a0f1ff986e3944fca4dbb3a73cc742b4cb8aac49720d6c960ec38ba8998
Tx public key: dd0cb2ecf546c5598fff5c4d32a5f33675c32719193c7b3af9e804a3df260ca1
Timestamp: 1709540100 Timestamp [UCT]: 2024-03-04 08:15:00 Age [y:d:h:m:s]: 00:325:22:21:11
Block: 970850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233261 RingCT/type: yes/0
Extra: 01dd0cb2ecf546c5598fff5c4d32a5f33675c32719193c7b3af9e804a3df260ca10211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34c532b40cb66326c96627054f3046fdc236bed8e81ae6ec134553e82e711a14 0.600000000000 1430713 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": 970860, "vin": [ { "gen": { "height": 970850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34c532b40cb66326c96627054f3046fdc236bed8e81ae6ec134553e82e711a14" } } ], "extra": [ 1, 221, 12, 178, 236, 245, 70, 197, 89, 143, 255, 92, 77, 50, 165, 243, 54, 117, 195, 39, 25, 25, 60, 123, 58, 249, 232, 4, 163, 223, 38, 12, 161, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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