Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e503a726010534966a20c1b6d3999dc1e5ad9a92b1970a13d929a97f59e754b

Tx prefix hash: 3c32c74ae4bc4cb89e41ecd2c922878c9db68f0d5cdd33e1a8c8cd52b7ffb3e9
Tx public key: 429c25a157d6c26a9bd4e190ed17083effab062da530ccfba2216f2aab493c6f
Timestamp: 1675635936 Timestamp [UCT]: 2023-02-05 22:25:36 Age [y:d:h:m:s]: 02:057:22:23:41
Block: 690640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 563013 RingCT/type: yes/0
Extra: 01429c25a157d6c26a9bd4e190ed17083effab062da530ccfba2216f2aab493c6f0211000000015029cbac000000000000000000

1 output(s) for total of 3.159533094000 dcy

stealth address amount amount idx
00: 7204fa01635e1f8e54002c7215bbb11226bfb15f950cae76b25468c955ca967a 3.159533094000 1133374 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": 690650, "vin": [ { "gen": { "height": 690640 } } ], "vout": [ { "amount": 3159533094, "target": { "key": "7204fa01635e1f8e54002c7215bbb11226bfb15f950cae76b25468c955ca967a" } } ], "extra": [ 1, 66, 156, 37, 161, 87, 214, 194, 106, 155, 212, 225, 144, 237, 23, 8, 62, 255, 171, 6, 45, 165, 48, 204, 251, 162, 33, 111, 42, 171, 73, 60, 111, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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