Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdc1544ab2a35226e8133324a86bd18d945bebb0f8886a63395ea208ea8a46ef

Tx prefix hash: c5aad33ad6071c09d7b3b3c3d55619550fd8265c2f1d696db2c945311355cf40
Tx public key: 88f506e8e539dcfa5392c879e1b10220be9d33077c2c5dcce00156d28f1fce90
Timestamp: 1706752759 Timestamp [UCT]: 2024-02-01 01:59:19 Age [y:d:h:m:s]: 01:025:08:15:59
Block: 947710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279158 RingCT/type: yes/0
Extra: 0188f506e8e539dcfa5392c879e1b10220be9d33077c2c5dcce00156d28f1fce900211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c00ff26dacdd7d58447a07c320c97949dd2a4323e5e3d576ae1c5f4f8a1e715b 0.600000000000 1406068 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": 947720, "vin": [ { "gen": { "height": 947710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c00ff26dacdd7d58447a07c320c97949dd2a4323e5e3d576ae1c5f4f8a1e715b" } } ], "extra": [ 1, 136, 245, 6, 232, 229, 57, 220, 250, 83, 146, 200, 121, 225, 177, 2, 32, 190, 157, 51, 7, 124, 44, 93, 204, 224, 1, 86, 210, 143, 31, 206, 144, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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