Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc5402633a6b0f7295aa1e7c6626fe3e2e7fc7543dd767cd2ce9632bb9247ec6

Tx prefix hash: 10dc5b291e3f9fbc1b24fa01ff4ac6fc9043b7472c8d3adff8f60c06b782282b
Tx public key: 07b37008bb59a6f78ad0034446262303ccc0d217ade009a9b05524058b54d5c5
Timestamp: 1728675423 Timestamp [UCT]: 2024-10-11 19:37:03 Age [y:d:h:m:s]: 00:179:06:41:35
Block: 1129483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127908 RingCT/type: yes/0
Extra: 0107b37008bb59a6f78ad0034446262303ccc0d217ade009a9b05524058b54d5c5021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09642cbc36d1283b3aadce7c1d4c432f3d242a05ba6860e6aa79bf1ca2675845 0.600000000000 1612310 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": 1129493, "vin": [ { "gen": { "height": 1129483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09642cbc36d1283b3aadce7c1d4c432f3d242a05ba6860e6aa79bf1ca2675845" } } ], "extra": [ 1, 7, 179, 112, 8, 187, 89, 166, 247, 138, 208, 3, 68, 70, 38, 35, 3, 204, 192, 210, 23, 173, 224, 9, 169, 176, 85, 36, 5, 139, 84, 213, 197, 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