Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a421849df3c199449cdcf5e08ab76922ee44e9500d6c0c6dad3b28169596c67

Tx prefix hash: 2b6109efc5f2de8e8185ada426ece4b3a66bb89468a26c481d39003099e582f9
Tx public key: dedfbb103a130eedce0d803b0c218d2c471a67518e8175bda17dc7d64034b232
Timestamp: 1703863971 Timestamp [UCT]: 2023-12-29 15:32:51 Age [y:d:h:m:s]: 01:175:11:25:15
Block: 923775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386382 RingCT/type: yes/0
Extra: 01dedfbb103a130eedce0d803b0c218d2c471a67518e8175bda17dc7d64034b2320211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3da41dcbeaead8d0457a69d6e7b8a5c9ae759b0c3e7370db1c44db6837bee9c 0.600000000000 1381511 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": 923785, "vin": [ { "gen": { "height": 923775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3da41dcbeaead8d0457a69d6e7b8a5c9ae759b0c3e7370db1c44db6837bee9c" } } ], "extra": [ 1, 222, 223, 187, 16, 58, 19, 14, 237, 206, 13, 128, 59, 12, 33, 141, 44, 71, 26, 103, 81, 142, 129, 117, 189, 161, 125, 199, 214, 64, 52, 178, 50, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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