Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 178b5cfd400d14ed45593aa241b253a7e856bc5d3fc61e0e362f174026451f38

Tx prefix hash: 16e608e0b4651d3f989eb2849961a52f8a219f73877c81a4b773fcd32113db77
Tx public key: fcf5b8bb2fd766c5107617b5731fef972b21fc9b14cce3aa56bce35719a050a8
Timestamp: 1704751675 Timestamp [UCT]: 2024-01-08 22:07:55 Age [y:d:h:m:s]: 01:015:17:08:26
Block: 931116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272534 RingCT/type: yes/0
Extra: 01fcf5b8bb2fd766c5107617b5731fef972b21fc9b14cce3aa56bce35719a050a802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 244f57231222620732e1757e4fd783f008ceb29341acf2ab18fdc905d397f3e8 0.600000000000 1389008 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": 931126, "vin": [ { "gen": { "height": 931116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "244f57231222620732e1757e4fd783f008ceb29341acf2ab18fdc905d397f3e8" } } ], "extra": [ 1, 252, 245, 184, 187, 47, 215, 102, 197, 16, 118, 23, 181, 115, 31, 239, 151, 43, 33, 252, 155, 20, 204, 227, 170, 86, 188, 227, 87, 25, 160, 80, 168, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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