Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f817e797816e1f6ebc573f78a0f9b8204f2aed3d04c83e56f1c9b4e92042631

Tx prefix hash: f5b2fe70d98e3ca40c2d2d808ce890a83c433fa19bb3851e8cebd8264e305384
Tx public key: 119584d51b2583d49a45ac653de6fb631b862496e965f53e2ec758edb456785b
Timestamp: 1680852780 Timestamp [UCT]: 2023-04-07 07:33:00 Age [y:d:h:m:s]: 01:281:06:29:25
Block: 733500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462287 RingCT/type: yes/0
Extra: 01119584d51b2583d49a45ac653de6fb631b862496e965f53e2ec758edb456785b0211000000015029cbac000000000000000000

1 output(s) for total of 2.278296469000 dcy

stealth address amount amount idx
00: 1fc43d76416f3f4c1ee2028f6b12d1a2d0a573667c0f538e0e32effda74a4e5c 2.278296469000 1179567 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": 733510, "vin": [ { "gen": { "height": 733500 } } ], "vout": [ { "amount": 2278296469, "target": { "key": "1fc43d76416f3f4c1ee2028f6b12d1a2d0a573667c0f538e0e32effda74a4e5c" } } ], "extra": [ 1, 17, 149, 132, 213, 27, 37, 131, 212, 154, 69, 172, 101, 61, 230, 251, 99, 27, 134, 36, 150, 233, 101, 245, 62, 46, 199, 88, 237, 180, 86, 120, 91, 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