Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f67673a469dfa9923e393e0637968cd9f52b36dc5620bc7cf802acc7ba9e22e3

Tx prefix hash: 408f78c8eff59a252fb2fb8d2ef55db751aec1378daeaeb7a083923adf41ed37
Tx public key: 00c46f32b082642f2e0df4310a2acd1c6956e4f5f71f7f4fc353f06d47bdeda1
Timestamp: 1685303215 Timestamp [UCT]: 2023-05-28 19:46:55 Age [y:d:h:m:s]: 01:233:20:31:54
Block: 770151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428559 RingCT/type: yes/0
Extra: 0100c46f32b082642f2e0df4310a2acd1c6956e4f5f71f7f4fc353f06d47bdeda1021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.722543530000 dcy

stealth address amount amount idx
00: 5fff399941cbd4f66647fed781e412846ab26b545b77c11f72bbfb5bf8892e7e 1.722543530000 1219438 of 0

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": 770161, "vin": [ { "gen": { "height": 770151 } } ], "vout": [ { "amount": 1722543530, "target": { "key": "5fff399941cbd4f66647fed781e412846ab26b545b77c11f72bbfb5bf8892e7e" } } ], "extra": [ 1, 0, 196, 111, 50, 176, 130, 100, 47, 46, 13, 244, 49, 10, 42, 205, 28, 105, 86, 228, 245, 247, 31, 127, 79, 195, 83, 240, 109, 71, 189, 237, 161, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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