Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d795cbaed42f49b3da1775ca618d36f7de475a68e9156acd78b3aa8e5907ec9

Tx prefix hash: a2c5454990b86e452c34d7adcaf5068a34798b1c2c2109c37bba0a77090d92f1
Tx public key: 7d42ea446bb3f1533565df68f1d321a14e26caf8dd30c35cee18921259e9bc00
Timestamp: 1705062774 Timestamp [UCT]: 2024-01-12 12:32:54 Age [y:d:h:m:s]: 01:116:08:08:26
Block: 933705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344271 RingCT/type: yes/0
Extra: 017d42ea446bb3f1533565df68f1d321a14e26caf8dd30c35cee18921259e9bc000211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbefdae26e55e30d8bc826b70ee6bf4ea15dde3f880d299f9253322b75c02ea2 0.600000000000 1391675 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": 933715, "vin": [ { "gen": { "height": 933705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbefdae26e55e30d8bc826b70ee6bf4ea15dde3f880d299f9253322b75c02ea2" } } ], "extra": [ 1, 125, 66, 234, 68, 107, 179, 241, 83, 53, 101, 223, 104, 241, 211, 33, 161, 78, 38, 202, 248, 221, 48, 195, 92, 238, 24, 146, 18, 89, 233, 188, 0, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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