Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec18b9b7767236c54cd5d551d911644e543bc672e2b286817282755824ccf3f0

Tx prefix hash: c3619038f42d18a7ba3f120b6594ebc7653a6e47028119f6e7751343233f7200
Tx public key: f5da9c8545e7f5c81238796a74df9aeb08a5d81c5110b4a2abdfd5808e59d5e8
Timestamp: 1694997674 Timestamp [UCT]: 2023-09-18 00:41:14 Age [y:d:h:m:s]: 01:123:18:48:43
Block: 850468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349740 RingCT/type: yes/0
Extra: 01f5da9c8545e7f5c81238796a74df9aeb08a5d81c5110b4a2abdfd5808e59d5e8021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.933354286000 dcy

stealth address amount amount idx
00: eed411eb53007b7a2acf352f41c23edb1bcd380dcdbd65c15b62f403801de9b3 0.933354286000 1304188 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": 850478, "vin": [ { "gen": { "height": 850468 } } ], "vout": [ { "amount": 933354286, "target": { "key": "eed411eb53007b7a2acf352f41c23edb1bcd380dcdbd65c15b62f403801de9b3" } } ], "extra": [ 1, 245, 218, 156, 133, 69, 231, 245, 200, 18, 56, 121, 106, 116, 223, 154, 235, 8, 165, 216, 28, 81, 16, 180, 162, 171, 223, 213, 128, 142, 89, 213, 232, 2, 17, 0, 0, 0, 7, 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