Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85b3de16a006eefddf0c714d39d37e22a5c5b8422ed656c28720038e9a4d966c

Tx prefix hash: 47845dac46843b6b49ca9a161748736a15ae4cb7c9ed7a3f1cd84a9208eb5c64
Tx public key: 7d8fa15806903549b87d2b00f62037a33fa3b89aa1336a0f4b4916b0d0c42daf
Timestamp: 1732136684 Timestamp [UCT]: 2024-11-20 21:04:44 Age [y:d:h:m:s]: 00:130:23:21:02
Block: 1158077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93423 RingCT/type: yes/0
Extra: 017d8fa15806903549b87d2b00f62037a33fa3b89aa1336a0f4b4916b0d0c42daf021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcfc6d5ea32f07dffcf31a4fd9a130360867c4e13c9148f19a1aa8074b80471e 0.600000000000 1643706 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": 1158087, "vin": [ { "gen": { "height": 1158077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcfc6d5ea32f07dffcf31a4fd9a130360867c4e13c9148f19a1aa8074b80471e" } } ], "extra": [ 1, 125, 143, 161, 88, 6, 144, 53, 73, 184, 125, 43, 0, 246, 32, 55, 163, 63, 163, 184, 154, 161, 51, 106, 15, 75, 73, 22, 176, 208, 196, 45, 175, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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