Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecaf3d24bf84670fdb4b0e25da8db843c5d6a2fd41ed8f95c979e7708391d6f7

Tx prefix hash: 617a9064f15fdbcfce4f3ae9a2e946170a268ff6ee37cf1fe17cfd899ff6ad62
Tx public key: 17b01233a5e89ab9330515de33bb959b044e2a26c157ec2fcbe969d51cb5dfef
Timestamp: 1716506046 Timestamp [UCT]: 2024-05-23 23:14:06 Age [y:d:h:m:s]: 00:324:22:59:45
Block: 1028590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232277 RingCT/type: yes/0
Extra: 0117b01233a5e89ab9330515de33bb959b044e2a26c157ec2fcbe969d51cb5dfef02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a45a5add5e19579bbc2b2d82a495837f18607b0b44b05f525591c1b2c8a7a319 0.600000000000 1496583 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": 1028600, "vin": [ { "gen": { "height": 1028590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a45a5add5e19579bbc2b2d82a495837f18607b0b44b05f525591c1b2c8a7a319" } } ], "extra": [ 1, 23, 176, 18, 51, 165, 232, 154, 185, 51, 5, 21, 222, 51, 187, 149, 155, 4, 78, 42, 38, 193, 87, 236, 47, 203, 233, 105, 213, 28, 181, 223, 239, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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