Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4561d3d78186fb98b76a0013776cd190090d113922a6e3adbc641d753030c2f1

Tx prefix hash: b3f67c4467644aa36eb4bb5d972c84eebf1c62404b677cbf68eabc63907105ab
Tx public key: a65bc2317c6898a31cfe5f8b8a682dd4b7451a4f081b62a7f13aa2da0504375a
Timestamp: 1714764519 Timestamp [UCT]: 2024-05-03 19:28:39 Age [y:d:h:m:s]: 00:335:00:48:54
Block: 1014151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239481 RingCT/type: yes/0
Extra: 01a65bc2317c6898a31cfe5f8b8a682dd4b7451a4f081b62a7f13aa2da0504375a0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfb76b9db7f4bda2f38288d5c27e62fe68584c5238891604d024036d655dac73 0.600000000000 1477160 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": 1014161, "vin": [ { "gen": { "height": 1014151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfb76b9db7f4bda2f38288d5c27e62fe68584c5238891604d024036d655dac73" } } ], "extra": [ 1, 166, 91, 194, 49, 124, 104, 152, 163, 28, 254, 95, 139, 138, 104, 45, 212, 183, 69, 26, 79, 8, 27, 98, 167, 241, 58, 162, 218, 5, 4, 55, 90, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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