Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edb010d95013d6c04e6cdddecc25d995b79c79180978c09b1a2e6c947261eef1

Tx prefix hash: 2167a7e7646d5d47aa1ab7f086022dcdd5565d433d4b339d8f80b8bdde5be453
Tx public key: 743f12e598eb8e258c917469d4638067cd81f82c6b0bb7570e62764bde3f1610
Timestamp: 1673231159 Timestamp [UCT]: 2023-01-09 02:25:59 Age [y:d:h:m:s]: 02:048:20:29:30
Block: 670669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556577 RingCT/type: yes/0
Extra: 01743f12e598eb8e258c917469d4638067cd81f82c6b0bb7570e62764bde3f161002110000000252542ceb000000000000000000

1 output(s) for total of 3.679553749000 dcy

stealth address amount amount idx
00: dae1bdc4e6998a5ea64d9ccf9acd54dc69648fb1ecbf5096cb4cf68272d68a2c 3.679553749000 1112084 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": 670679, "vin": [ { "gen": { "height": 670669 } } ], "vout": [ { "amount": 3679553749, "target": { "key": "dae1bdc4e6998a5ea64d9ccf9acd54dc69648fb1ecbf5096cb4cf68272d68a2c" } } ], "extra": [ 1, 116, 63, 18, 229, 152, 235, 142, 37, 140, 145, 116, 105, 212, 99, 128, 103, 205, 129, 248, 44, 107, 11, 183, 87, 14, 98, 118, 75, 222, 63, 22, 16, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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