Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ff958d0f5bd6495fb5912734cf8f9ae72a38c1ba5d1465a0faf41bd43b1923e

Tx prefix hash: 53c2d15455ebdad44573a1fa4747696341cacf297fde6c7ea6a04edce71c8a99
Tx public key: 06760d28947329ca59b7eee9e2cacf03093741b562ac9eaa7c814f68dbedd3df
Timestamp: 1669134832 Timestamp [UCT]: 2022-11-22 16:33:52 Age [y:d:h:m:s]: 02:003:00:53:57
Block: 636756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524073 RingCT/type: yes/0
Extra: 0106760d28947329ca59b7eee9e2cacf03093741b562ac9eaa7c814f68dbedd3df02110000000183600029000000000000000000

1 output(s) for total of 4.766098877000 dcy

stealth address amount amount idx
00: f8606c3fa5bd1e6c9cdb95197a22727903b262d34745700fcf4f24adbd27d8b5 4.766098877000 1076224 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": 636766, "vin": [ { "gen": { "height": 636756 } } ], "vout": [ { "amount": 4766098877, "target": { "key": "f8606c3fa5bd1e6c9cdb95197a22727903b262d34745700fcf4f24adbd27d8b5" } } ], "extra": [ 1, 6, 118, 13, 40, 148, 115, 41, 202, 89, 183, 238, 233, 226, 202, 207, 3, 9, 55, 65, 181, 98, 172, 158, 170, 124, 129, 79, 104, 219, 237, 211, 223, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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