Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99268bbb8d01f26d5600a758afaba91bed367e808959c7e4b06634e53aa786c5

Tx prefix hash: 5566e6432d67e29109bce742577a65131f57c50d4bf08bcf4ef9ecc0ce43a46a
Tx public key: 92a5de06f8b68cc611ff9a3658da9d59d796d5df51e725b6ac59ccf39ef2a095
Timestamp: 1729154484 Timestamp [UCT]: 2024-10-17 08:41:24 Age [y:d:h:m:s]: 00:228:13:58:34
Block: 1133449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163192 RingCT/type: yes/0
Extra: 0192a5de06f8b68cc611ff9a3658da9d59d796d5df51e725b6ac59ccf39ef2a095021100000004e914dd15000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 417c70c7300a0fd247a2cfd3352b564f376808d423f77ba14f1619e153440690 0.600010000000 1616566 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": 1133459, "vin": [ { "gen": { "height": 1133449 } } ], "vout": [ { "amount": 600010000, "target": { "key": "417c70c7300a0fd247a2cfd3352b564f376808d423f77ba14f1619e153440690" } } ], "extra": [ 1, 146, 165, 222, 6, 248, 182, 140, 198, 17, 255, 154, 54, 88, 218, 157, 89, 215, 150, 213, 223, 81, 231, 37, 182, 172, 89, 204, 243, 158, 242, 160, 149, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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