Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 785367238b30420f83a8285ae6d13889cd0a0412cd4132a7c4fa0afb10a03d91

Tx prefix hash: a5834e5d7d930c1829d2e58bda832d9f2921c18aed7b8b79ee3ffed8abf86875
Tx public key: 1e6ff2cc1e4c5b43057e6aa0c1033099bced8422d5457a6fa6335d44f206e5aa
Timestamp: 1583749631 Timestamp [UCT]: 2020-03-09 10:27:11 Age [y:d:h:m:s]: 04:253:05:06:02
Block: 78974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076066 RingCT/type: yes/0
Extra: 011e6ff2cc1e4c5b43057e6aa0c1033099bced8422d5457a6fa6335d44f206e5aa0211000000066d997e00000000000000000000

1 output(s) for total of 335.990614288000 dcy

stealth address amount amount idx
00: 2b22057f844f6f749fcbd81c3b79e3d301ca564675246f6dc10983d50dc453a1 335.990614288000 144694 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": 78984, "vin": [ { "gen": { "height": 78974 } } ], "vout": [ { "amount": 335990614288, "target": { "key": "2b22057f844f6f749fcbd81c3b79e3d301ca564675246f6dc10983d50dc453a1" } } ], "extra": [ 1, 30, 111, 242, 204, 30, 76, 91, 67, 5, 126, 106, 160, 193, 3, 48, 153, 188, 237, 132, 34, 213, 69, 122, 111, 166, 51, 93, 68, 242, 6, 229, 170, 2, 17, 0, 0, 0, 6, 109, 153, 126, 0, 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