Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfb432441edfad69c51713a8088dec7c4b1d23136973bcdbaf46bb57f62f34b5

Tx prefix hash: 8560e9879349cabfc7faf2ccce7dee9e97d483e45df9555cbb535f28ddc7694d
Tx public key: 7b3cd09abc9e74058c093bff9e3309fd83b3bd14679f8d2eb0c4dd40d5db365d
Timestamp: 1727309828 Timestamp [UCT]: 2024-09-26 00:17:08 Age [y:d:h:m:s]: 00:229:17:40:53
Block: 1118156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164037 RingCT/type: yes/0
Extra: 017b3cd09abc9e74058c093bff9e3309fd83b3bd14679f8d2eb0c4dd40d5db365d021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 113bbdf2cd8eb685465c98c44b7544acb9465c4bc34d9b756ca7e0cea47e32a4 0.600000000000 1599251 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": 1118166, "vin": [ { "gen": { "height": 1118156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "113bbdf2cd8eb685465c98c44b7544acb9465c4bc34d9b756ca7e0cea47e32a4" } } ], "extra": [ 1, 123, 60, 208, 154, 188, 158, 116, 5, 140, 9, 59, 255, 158, 51, 9, 253, 131, 179, 189, 20, 103, 159, 141, 46, 176, 196, 221, 64, 213, 219, 54, 93, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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