Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dcc3131d37b0590d684ca1ce78a86c2f2166302bd62696cc7a4db1b694b5df8

Tx prefix hash: 6bf181afbf7c4c4937c9eb6ba15643f821f5efac2d90bcf53709f1718b15e298
Tx public key: 54078b0ed61c0a9b64da7ecd541b9dc2e547032f2aad602504b3fc0349da0248
Timestamp: 1723633139 Timestamp [UCT]: 2024-08-14 10:58:59 Age [y:d:h:m:s]: 01:092:05:46:54
Block: 1087679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324390 RingCT/type: yes/0
Extra: 0154078b0ed61c0a9b64da7ecd541b9dc2e547032f2aad602504b3fc0349da024802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae9fbff26828b4048bb7e4d48869cd555790f51dc5483c4a43aa15de9c53d635 0.600000000000 1562290 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": 1087689, "vin": [ { "gen": { "height": 1087679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae9fbff26828b4048bb7e4d48869cd555790f51dc5483c4a43aa15de9c53d635" } } ], "extra": [ 1, 84, 7, 139, 14, 214, 28, 10, 155, 100, 218, 126, 205, 84, 27, 157, 194, 229, 71, 3, 47, 42, 173, 96, 37, 4, 179, 252, 3, 73, 218, 2, 72, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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