Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c405859cf7616a5047ee0b1ad0e6ca028101ee70b05d81f5cdbc569f5bad5638

Tx prefix hash: b44568f92e9abcf82948a7e198933d65177b60f693c5cca357ef1a916bdc02ec
Tx public key: b6192933d56c32b938d2e681d2955e39ada29d0e2713f3678cd8611afe476804
Timestamp: 1680941223 Timestamp [UCT]: 2023-04-08 08:07:03 Age [y:d:h:m:s]: 02:031:20:28:36
Block: 734118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544796 RingCT/type: yes/0
Extra: 01b6192933d56c32b938d2e681d2955e39ada29d0e2713f3678cd8611afe476804021100000003b3164c24000000000000000000

1 output(s) for total of 2.267579622000 dcy

stealth address amount amount idx
00: 940ea4ce0e278bc1c61eb2b34b80c2f7e51bb630b956ea01da52aacd6c61d8f2 2.267579622000 1180269 of 0

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": 734128, "vin": [ { "gen": { "height": 734118 } } ], "vout": [ { "amount": 2267579622, "target": { "key": "940ea4ce0e278bc1c61eb2b34b80c2f7e51bb630b956ea01da52aacd6c61d8f2" } } ], "extra": [ 1, 182, 25, 41, 51, 213, 108, 50, 185, 56, 210, 230, 129, 210, 149, 94, 57, 173, 162, 157, 14, 39, 19, 243, 103, 140, 216, 97, 26, 254, 71, 104, 4, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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