Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e7c91be93623e31ee6131e58c8a2b0d9db8fbbd22b45a13b2590aacab4f9c51

Tx prefix hash: 695899ea5a98983b45f3a5160fd04bcbd44234032cf2904954f3d050d93ba82a
Tx public key: ca165ae08caca86f5e58e88f86f0adf54f0313224e96ec81a1173f9ad2be76b5
Timestamp: 1728873499 Timestamp [UCT]: 2024-10-14 02:38:19 Age [y:d:h:m:s]: 01:051:14:45:51
Block: 1131123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295305 RingCT/type: yes/0
Extra: 01ca165ae08caca86f5e58e88f86f0adf54f0313224e96ec81a1173f9ad2be76b502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39f769b4a22890d8b797d52ba27688ff5b222b13bcf698a661c9520ebd2bb1c7 0.600000000000 1614004 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": 1131133, "vin": [ { "gen": { "height": 1131123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39f769b4a22890d8b797d52ba27688ff5b222b13bcf698a661c9520ebd2bb1c7" } } ], "extra": [ 1, 202, 22, 90, 224, 140, 172, 168, 111, 94, 88, 232, 143, 134, 240, 173, 245, 79, 3, 19, 34, 78, 150, 236, 129, 161, 23, 63, 154, 210, 190, 118, 181, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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