Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb71ca7fb35830e069406d071b55de7f28b07676057de6bd86218d9cde486cd8

Tx prefix hash: 3e5b35c5ee7af42cc7946becf66ae4408f2d8fd6dc584443979c6c4290434495
Tx public key: ed80b13980fdc24802c1c2542f5d267d28ea4ea475134ecd88cc1ccc7dea198b
Timestamp: 1727610626 Timestamp [UCT]: 2024-09-29 11:50:26 Age [y:d:h:m:s]: 00:055:15:49:58
Block: 1120657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39767 RingCT/type: yes/0
Extra: 01ed80b13980fdc24802c1c2542f5d267d28ea4ea475134ecd88cc1ccc7dea198b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 907ce93ed4e904018a8f8fad29c03aa7e06e52ec695ed1e64811511538d840fc 0.600000000000 1602650 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": 1120667, "vin": [ { "gen": { "height": 1120657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "907ce93ed4e904018a8f8fad29c03aa7e06e52ec695ed1e64811511538d840fc" } } ], "extra": [ 1, 237, 128, 177, 57, 128, 253, 194, 72, 2, 193, 194, 84, 47, 93, 38, 125, 40, 234, 78, 164, 117, 19, 78, 205, 136, 204, 28, 204, 125, 234, 25, 139, 2, 17, 0, 0, 0, 3, 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