Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7218e385a5f7100e08513f812a0e842c28b5bd7a0f60563a90406f032e61555

Tx prefix hash: f29ccde0f686b4f4b6b40d9b4a810433ee4ff4dbab94476f43dad853040ece11
Tx public key: f41768acc27826c401d6d50bcc9db02496414d73a4ad4956a98d63d67d794b97
Timestamp: 1637850806 Timestamp [UCT]: 2021-11-25 14:33:26 Age [y:d:h:m:s]: 03:340:21:34:03
Block: 381879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1020044 RingCT/type: yes/0
Extra: 01f41768acc27826c401d6d50bcc9db02496414d73a4ad4956a98d63d67d794b9702110000001dd6e4826b000000000000000000

1 output(s) for total of 33.318411345000 dcy

stealth address amount amount idx
00: 0ec3c1d5668363cb2dc814c24aa4d9fb34c9507839a05819ddf2808d201ae70b 33.318411345000 771356 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": 381889, "vin": [ { "gen": { "height": 381879 } } ], "vout": [ { "amount": 33318411345, "target": { "key": "0ec3c1d5668363cb2dc814c24aa4d9fb34c9507839a05819ddf2808d201ae70b" } } ], "extra": [ 1, 244, 23, 104, 172, 194, 120, 38, 196, 1, 214, 213, 11, 204, 157, 176, 36, 150, 65, 77, 115, 164, 173, 73, 86, 169, 141, 99, 214, 125, 121, 75, 151, 2, 17, 0, 0, 0, 29, 214, 228, 130, 107, 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