Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72ac20a3925b3a495cd816116d49607ef1aeb1944149fb2c332ed2c3225f8374

Tx prefix hash: 2fee7f39378b5a074acebad47f575433b66d5d39b8b81819dd33276f79f4b40f
Tx public key: 0275ac1169b4e6bb6b4d30e8cc117df5ebc90170fabfa681b0c9f494df3a69bb
Timestamp: 1734303896 Timestamp [UCT]: 2024-12-15 23:04:56 Age [y:d:h:m:s]: 00:094:00:20:39
Block: 1176054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66978 RingCT/type: yes/0
Extra: 010275ac1169b4e6bb6b4d30e8cc117df5ebc90170fabfa681b0c9f494df3a69bb0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4bb86afae45beb07b8439a1ed58b14b5cafd0900bc885e394c39c08b7c56e74 0.600000000000 1662383 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": 1176064, "vin": [ { "gen": { "height": 1176054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4bb86afae45beb07b8439a1ed58b14b5cafd0900bc885e394c39c08b7c56e74" } } ], "extra": [ 1, 2, 117, 172, 17, 105, 180, 230, 187, 107, 77, 48, 232, 204, 17, 125, 245, 235, 201, 1, 112, 250, 191, 166, 129, 176, 201, 244, 148, 223, 58, 105, 187, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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