Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 879c20688055618dfb218c5822297b591f0280aca2d1e06cef359410a489aa48

Tx prefix hash: 1c05af7ee76b53b57fe2f1fb8634dc641264855277858c3306078d5e5a8f6a9d
Tx public key: ebf6e58fd4430e3015174f3148fd1f9de52751b52b2a2e52fc93af52ac9b31ef
Timestamp: 1711980815 Timestamp [UCT]: 2024-04-01 14:13:35 Age [y:d:h:m:s]: 01:057:13:46:02
Block: 991041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302183 RingCT/type: yes/0
Extra: 01ebf6e58fd4430e3015174f3148fd1f9de52751b52b2a2e52fc93af52ac9b31ef02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a82aab21509cc8266300d8e9c68b75ddc133fe30ca60c5dbb50baba7d26b12c9 0.600000000000 1451373 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": 991051, "vin": [ { "gen": { "height": 991041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a82aab21509cc8266300d8e9c68b75ddc133fe30ca60c5dbb50baba7d26b12c9" } } ], "extra": [ 1, 235, 246, 229, 143, 212, 67, 14, 48, 21, 23, 79, 49, 72, 253, 31, 157, 229, 39, 81, 181, 43, 42, 46, 82, 252, 147, 175, 82, 172, 155, 49, 239, 2, 17, 0, 0, 0, 7, 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