Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2855a39bf71aa092e4abf7e6290a8e5dd2f853c342c32a361c72559b33242b9

Tx prefix hash: 68952e3a1b81c9a499cbca7a59c6a40ecb1c7aa3021fb9de770439d4eae0be5a
Tx public key: b5c684ebe1183a2f4da6b967ecbcdc5d4501a3385bc99a271bb16575de4285a1
Timestamp: 1707370025 Timestamp [UCT]: 2024-02-08 05:27:05 Age [y:d:h:m:s]: 01:019:04:23:01
Block: 952839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274729 RingCT/type: yes/0
Extra: 01b5c684ebe1183a2f4da6b967ecbcdc5d4501a3385bc99a271bb16575de4285a102110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 923e81f35734d33bcfbb548ef65a27d75ee63b98412d73799ccd2dba90fd3368 0.600000000000 1411971 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": 952849, "vin": [ { "gen": { "height": 952839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "923e81f35734d33bcfbb548ef65a27d75ee63b98412d73799ccd2dba90fd3368" } } ], "extra": [ 1, 181, 198, 132, 235, 225, 24, 58, 47, 77, 166, 185, 103, 236, 188, 220, 93, 69, 1, 163, 56, 91, 201, 154, 39, 27, 177, 101, 117, 222, 66, 133, 161, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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