Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fee6bb1fc699d70fd799a752694f257f1872f21b2665a8b6e111ace283d1c006

Tx prefix hash: aa6c5592cfb52f7aa3a3a90bf7942e45cfdba57079ea85ccab07d7c7038ff19a
Tx public key: f37b7ad01855b88fdfa166ecd1a61b02af1bf06bcee81083f260d6ed0f777fc0
Timestamp: 1728145999 Timestamp [UCT]: 2024-10-05 16:33:19 Age [y:d:h:m:s]: 00:083:19:03:20
Block: 1125091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59894 RingCT/type: yes/0
Extra: 01f37b7ad01855b88fdfa166ecd1a61b02af1bf06bcee81083f260d6ed0f777fc002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 897dbc8779c01f2523a264fa9c4385691869aaeee223a5a713eba7c4d612937f 0.600000000000 1607764 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": 1125101, "vin": [ { "gen": { "height": 1125091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "897dbc8779c01f2523a264fa9c4385691869aaeee223a5a713eba7c4d612937f" } } ], "extra": [ 1, 243, 123, 122, 208, 24, 85, 184, 143, 223, 161, 102, 236, 209, 166, 27, 2, 175, 27, 240, 107, 206, 232, 16, 131, 242, 96, 214, 237, 15, 119, 127, 192, 2, 17, 0, 0, 0, 5, 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